There was a question on the previous PR about why description|header|preheader were limited to strings. (same applies to DialogHeader)

IMO string is the right choice here. The design is very deliberate about only allowing text content in these sections, and I don't think there's a scenario where we would want users to be able to inject any component they like here.

@joshwooding @origami-z @navkaur76 thoughts?

In most cases, pure string would be provided anyway. However, in case teams want to put additional layout, icon or other relevant stuff, we could try to accommodate? A few other components does this

I would rather use ReactNode or something similar. It's not worth being restrictive

@joshwooding following up on question from previous PR: "Is "body" the correct way to refer to this?"

I think it is, as it's the body of the header (multiple text elements that are wrapped together, discrete from the end adornment). Not a strongly-help opinion, though, so happy to hear counter arguments 😄

It needs to be aligned with design @navkaur76

In figma, the frame containing the main heading, pre-header and description is called "Block", if that helps? The accent bar sits outside of this frame.

Closest block in the system is in stepper input?

Using endAdornment to be consistent with other components. Are there any strong opinions about the name? @joshwooding @origami-z

adornment is really only form controls previously... how does design refer to this? @navkaur76

It's "Close button" in figma

Adornment is also used in grid corner triangle? @bhoppers2008